Reviewing files that changed from the base of the PR and between 6dc26b4 and d65d2bb.

• packages/platform/atoms/booker/BookerPlatformWrapper.tsx (2 hunks)

packages/platform/atoms/booker/BookerPlatformWrapper.tsx (1)

598-603: Allow null/undefined and trim inputs in formatUsername

Use:

export function formatUsername(username: string | string[] | null | undefined): string {
  if (!username) return "";
  if (typeof username === "string") return username.trim();
  return username.filter(Boolean).map((u) => u.trim()).join("+");
}

Before merging, confirm there are no other definitions/imports/usages of formatUsername by running locally:
rg -n --hidden -S 'export\s+(const|function)\s+formatUsername' --glob '!node_modules/' || true
rg -n --hidden -S 'import.*formatUsername' --glob '!node_modules/' || true
rg -n --hidden -S '\bformatUsername\b' --glob '!node_modules/**' || true

Reviewing files that changed from the base of the PR and between d65d2bb and c940118.

• packages/platform/atoms/calendar-view/wrappers/CalendarViewPlatformWrapper.tsx (1 hunks)

• GitHub Check: Production builds / Build Atoms
• GitHub Check: Production builds / Build Web App
• GitHub Check: Production builds / Build API v2
• GitHub Check: Type check / check-types
• GitHub Check: Production builds / Build API v1
• GitHub Check: Linters / lint
• GitHub Check: Tests / Unit

packages/platform/atoms/calendar-view/wrappers/CalendarViewPlatformWrapper.tsx (5)

32-34: Confirm the consolidated type approach is correct.

The component accepts either individual or team props via union type, which looks good. The previous issue with isTeamEvent?: false preventing passing true appears to have been addressed based on the commit message.

---

193-211: Good component structure with proper store context usage.

The component properly uses the AtomsWrapper, BookerSection components with appropriate areas, and passes the required data to child components. The sticky positioning and z-index management look correct.

---

215-223: Clean wrapper implementation with proper store provider.

The wrapper component correctly provides the BookerStore context that's required by the child component. This separation of concerns is well done.

---

117-136: Extract URL search params logic to custom hook.

This duplicates logic from BookerPlatformWrapper. Consider creating a shared hook as suggested in the past review comment.

Create a custom hook useBookingRoutingParams to share this logic between CalendarViewPlatformWrapper and BookerPlatformWrapper:

export function useBookingRoutingParams(routingFormSearchParams?: URLSearchParams | string) {
  return useMemo(() => {
    const searchParams = routingFormSearchParams
      ? new URLSearchParams(routingFormSearchParams)
      : new URLSearchParams(window.location.search);
    
    const routedTeamMemberIds = getRoutedTeamMemberIdsFromSearchParams(searchParams);
    const skipContactOwner = searchParams.get("cal.skipContactOwner") === "true";
    const _cacheParam = searchParams?.get("cal.cache");
    const _shouldServeCache = _cacheParam ? _cacheParam === "true" : undefined;
    const isBookingDryRun =
      searchParams?.get("cal.isBookingDryRun")?.toLowerCase() === "true" ||
      searchParams?.get("cal.sandbox")?.toLowerCase() === "true";
    
    return {
      ...(skipContactOwner ? { skipContactOwner } : {}),
      ...(routedTeamMemberIds ? { routedTeamMemberIds } : {}),
      ...(_shouldServeCache ? { _shouldServeCache } : {}),
      ...(isBookingDryRun ? { isBookingDryRun } : {}),
    };
  }, [routingFormSearchParams]);
}

---

155-156: Clarify semantics and precedence of rescheduleUid vs bookingUid.

Search returned no repo matches here — confirm the intended rule when both props are supplied. Either document that rescheduleUid overrides bookingUid (add an inline comment and tests), or make the props mutually exclusive / consolidate/rename them to remove ambiguity.
Location: packages/platform/atoms/calendar-view/wrappers/CalendarViewPlatformWrapper.tsx (props mapping).